Audio encoder and decoder with dynamic range compression metadata

ABSTRACT

An audio processing unit (APU) is disclosed. The APU includes a buffer memory configured to store at least one frame of an encoded audio bitstream, where the encoded audio bitstream includes audio data and a metadata container. The metadata container includes a header and one or more metadata payloads after the header. The one or more metadata payloads include dynamic range compression (DRC) metadata, and the DRC metadata is or includes profile metadata indicative of whether the DRC metadata includes dynamic range compression (DRC) control values for use in performing dynamic range compression in accordance with at least one compression profile on audio content indicated by at least one block of the audio data.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/187,310, filed Jun. 20, 2016 which is a continuation of U.S. patentapplication Ser. No. 14/770,375, filed Aug. 25, 2015 which in turn isthe 371 national stage of PCT/US2014/042168, filed Jun. 12, 2014. PCTApplication No. PCT/US2014/042168 claims priority to U.S. ProvisionalPatent Application No. 61/836,865, filed on Jun. 19, 2013, each of whichis hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The invention pertains to audio signal processing, and moreparticularly, to encoding and decoding of audio data bitstreams withmetadata indicative of substream structure and/or program informationregarding audio content indicated by the bitstreams. Some embodiments ofthe invention generate or decode audio data in one of the formats knownas Dolby Digital (AC-3), Dolby Digital Plus (Enhanced AC-3 or E-AC-3),or Dolby E.

BACKGROUND OF THE INVENTION

Dolby, Dolby Digital, Dolby Digital Plus, and Dolby E are trademarks ofDolby Laboratories Licensing Corporation. Dolby Laboratories providesproprietary implementations of AC-3 and E-AC-3 known as Dolby Digitaland Dolby Digital Plus, respectively.

Audio data processing units typically operate in a blind fashion and donot pay attention to the processing history of audio data that occursbefore the data is received. This may work in a processing framework inwhich a single entity does all the audio data processing and encodingfor a variety of target media rendering devices while a target mediarendering device does all the decoding and rendering of the encodedaudio data. However, this blind processing does not work well (or atall) in situations where a plurality of audio processing units arescattered across a diverse network or are placed in tandem (i.e., chain)and are expected to optimally perform their respective types of audioprocessing. For example, some audio data may be encoded for highperformance media systems and may have to be converted to a reduced formsuitable for a mobile device along a media processing chain.Accordingly, an audio processing unit may unnecessarily perform a typeof processing on the audio data that has already been performed. Forinstance, a volume leveling unit may perform processing on an inputaudio clip, irrespective of whether or not the same or similar volumeleveling has been previously performed on the input audio clip. As aresult, the volume leveling unit may perform leveling even when it isnot necessary. This unnecessary processing may also cause degradationand/or the removal of specific features while rendering the content ofthe audio data.

BRIEF DESCRIPTION OF THE INVENTION

In a class of embodiments, the invention is an audio processing unitcapable of decoding an encoded bitstream that includes substreamstructure metadata and/or program information metadata (and optionallyalso other metadata, e.g., loudness processing state metadata) in atleast one segment of at least one frame of the bitstream and audio datain at least one other segment of the frame. Herein, substream structuremetadata (or “SSM”) denotes metadata of an encoded bitstream (or set ofencoded bitstreams) indicative of substream structure of audio contentof the encoded bitstream(s), and “program information metadata” (or“PIM”) denotes metadata of an encoded audio bitstream indicative of atleast one audio program (e.g., two or more audio programs), where theprogram information metadata is indicative of at least one property orcharacteristic of audio content of at least one said program (e.g.,metadata indicating a type or parameter of processing performed on audiodata of the program or metadata indicating which channels of the programare active channels).

In typical cases (e.g., in which the encoded bitstream is an AC-3 orE-AC-3 bitstream), the program information metadata (PIM) is indicativeof program information which cannot practically be carried in otherportions of the bitstream. For example, the PIM may be indicative ofprocessing applied to PCM audio prior to encoding (e.g., AC-3 or E-AC-3encoding), which frequency bands of the audio program have been encodedusing specific audio coding techniques, and the compression profile usedto create dynamic range compression (DRC) data in the bitstream.

In another class of embodiments, a method includes a step ofmultiplexing encoded audio data with SSM and/or PIM in each frame (oreach of at least some frames) of the bitstream. In typical decoding, adecoder extracts the SSM and/or PIM from the bitstream (including byparsing and demultiplexing the SSM and/or PIM and the audio data) andprocesses the audio data to generate a stream of decoded audio data (andin some cases also performs adaptive processing of the audio data). Insome embodiments, the decoded audio data and SSM and/or PIM areforwarded from the decoder to a post-processor configured to performadaptive processing on the decoded audio data using the SSM and/or PIM.

In a class of embodiments, the inventive encoding method generates anencoded audio bitstream (e.g., an AC-3 or E-AC-3 bitstream) includingaudio data segments (e.g., the AB0-AB5 segments of the frame shown inFIG. 4 or all or some of segments AB0-AB5 of the frame shown in FIG. 7)which includes encoded audio data, and metadata segments (including SSMand/or PIM, and optionally also other metadata) time divisionmultiplexed with the audio data segments. In some embodiments, eachmetadata segment (sometimes referred to herein as a “container”) has aformat which includes a metadata segment header (and optionally alsoother mandatory or “core” elements), and one or more metadata payloadsfollowing the metadata segment header. SIM, if present, is included inone of the metadata payloads (identified by a payload header, andtypically having format of a first type). PIM, if present, is includedin another one of the metadata payloads (identified by a payload headerand typically having format of a second type). Similarly, each othertype of metadata (if present) is included in another one of the metadatapayloads (identified by a payload header and typically having formatspecific to the type of metadata). The exemplary format allowsconvenient access to the SSM, PIM, and other metadata at times otherthan during decoding (e.g., by a post-processor following decoding, orby a processor configured to recognize the metadata without performingfull decoding on the encoded bitstream), and allows convenient andefficient error detection and correction (e.g., of substreamidentification) during decoding of the bitstream. For example, withoutaccess to SSM in the exemplary format, a decoder might incorrectlyidentify the correct number of substreams associated with a program. Onemetadata payload in a metadata segment may include SSM, another metadatapayload in the metadata segment may include PIM, and optionally also atleast one other metadata payload in the metadata segment may includeother metadata (e.g., loudness processing state metadata or “LPSM”).

In another class of embodiments, an audio processing unit (APU) isdisclosed. The APU includes a buffer memory configured to store at leastone frame of an encoded audio bitstream, where the encoded audiobitstream includes audio data and a metadata container. The metadatacontainer includes a header and one or more metadata payloads after theheader. The one or more metadata payloads include dynamic rangecompression (DRC) metadata, and the DRC metadata is or includes profilemetadata indicative of whether the DRC metadata includes dynamic rangecompression (DRC) control values for use in performing dynamic rangecompression in accordance with at least one compression profile on audiocontent indicated by at least one block of the audio data. If theprofile metadata indicates that the DRC metadata includes DRC controlvalues for use in performing dynamic range compression in accordancewith one said compression profile, the DRC metadata also includes a setof DRC control values generated in accordance with the compressionprofile. The APU also includes a parser coupled to the buffer memory andconfigured to parse the encoded audio bitstream. The APU furtherincludes a subsystem coupled to the parser and configured to performdynamic range compression, on at least some of the audio data or ondecoded audio data generated by decoding said at least some of the audiodata, using at least some of the DRC metadata.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an embodiment of a system which may beconfigured to perform an embodiment of the inventive method.

FIG. 2 is a block diagram of an encoder which is an embodiment of theinventive audio processing unit.

FIG. 3 is a block diagram of a decoder which is an embodiment of theinventive audio processing unit, and a post-processor coupled theretowhich is another embodiment of the inventive audio processing unit.

FIG. 4 is a diagram of an AC-3 frame, including the segments into whichit is divided.

FIG. 5 is a diagram of the Synchronization Information (SI) segment ofan AC-3 frame, including segments into which it is divided.

FIG. 6 is a diagram of the Bitstream Information (BSI) segment of anAC-3 frame, including segments into which it is divided.

FIG. 7 is a diagram of an E-AC-3 frame, including segments into which itis divided.

FIG. 8 is a diagram of a metadata segment of an encoded bitstreamgenerated in accordance with an embodiment of the invention, including ametadata segment header comprising a container sync word (identified as“container sync” in FIG. 8) and version and key ID values, followed bymultiple metadata payloads and protection bits.

NOTATION AND NOMENCLATURE

Throughout this disclosure, including in the claims, the expressionperforming an operation “on” a signal or data (e.g., filtering, scaling,transforming, or applying gain to, the signal or data) is used in abroad sense to denote performing the operation directly on the signal ordata, or on a processed version of the signal or data (e.g., on aversion of the signal that has undergone preliminary filtering orpre-processing prior to performance of the operation thereon).

Throughout this disclosure including in the claims, the expression“system” is used in a broad sense to denote a device, system, orsubsystem. For example, a subsystem that implements a decoder may bereferred to as a decoder system, and a system including such a subsystem(e.g., a system that generates X output signals in response to multipleinputs, in which the subsystem generates M of the inputs and the otherX−M inputs are received from an external source) may also be referred toas a decoder system.

Throughout this disclosure including in the claims, the term “processor”is used in a broad sense to denote a system or device programmable orotherwise configurable (e.g., with software or firmware) to performoperations on data (e.g., audio, or video or other image data). Examplesof processors include a field-programmable gate array (or otherconfigurable integrated circuit or chip set), a digital signal processorprogrammed and/or otherwise configured to perform pipelined processingon audio or other sound data, a programmable general purpose processoror computer, and a programmable microprocessor chip or chip set.

Throughout this disclosure including in the claims, the expressions“audio processor” and “audio processing unit” are used interchangeably,and in a broad sense, to denote a system configured to process audiodata. Examples of audio processing units include, but are not limited toencoders (e.g., transcoders), decoders, codecs, pre-processing systems,post-processing systems, and bitstream processing systems (sometimesreferred to as bitstream processing tools).

Throughout this disclosure including in the claims, the expression“metadata” (of an encoded audio bitstream) refers to separate anddifferent data from corresponding audio data of the bitstream.

Throughout this disclosure including in the claims, the expression“substream structure metadata” (or “SSM”) denotes metadata of an encodedaudio bitstream (or set of encoded audio bitstreams) indicative ofsubstream structure of audio content of the encoded bitstream(s).

Throughout this disclosure including in the claims, the expression“program information metadata” (or “PIM”) denotes metadata of an encodedaudio bitstream indicative of at least one audio program (e.g., two ormore audio programs), where said metadata is indicative of at least oneproperty or characteristic of audio content of at least one said program(e.g., metadata indicating a type or parameter of processing performedon audio data of the program or metadata indicating which channels ofthe program are active channels).

Throughout this disclosure including in the claims, the expression“processing state metadata” (e.g., as in the expression “loudnessprocessing state metadata”) refers to metadata (of an encoded audiobitstream) associated with audio data of the bitstream, indicates theprocessing state of corresponding (associated) audio data (e.g., whattype(s) of processing have already been performed on the audio data),and typically also indicates at least one feature or characteristic ofthe audio data. The association of the processing state metadata withthe audio data is time-synchronous. Thus, present (most recentlyreceived or updated) processing state metadata indicates that thecorresponding audio data contemporaneously comprises the results of theindicated type(s) of audio data processing. In some cases, processingstate metadata may include processing history and/or some or all of theparameters that are used in and/or derived from the indicated types ofprocessing. Additionally, processing state metadata may include at leastone feature or characteristic of the corresponding audio data, which hasbeen computed or extracted from the audio data. Processing statemetadata may also include other metadata that is not related to orderived from any processing of the corresponding audio data. Forexample, third party data, tracking information, identifiers,proprietary or standard information, user annotation data, userpreference data, etc. may be added by a particular audio processing unitto pass on to other audio processing units.

Throughout this disclosure including in the claims, the expression“loudness processing state metadata” (or “LPSM”) denotes processingstate metadata indicative of the loudness processing state ofcorresponding audio data (e.g. what type(s) of loudness processing havebeen performed on the audio data) and typically also at least onefeature or characteristic (e.g., loudness) of the corresponding audiodata. Loudness processing state metadata may include data (e.g., othermetadata) that is not (i.e., when it is considered alone) loudnessprocessing state metadata.

Throughout this disclosure including in the claims, the expression“channel” (or “audio channel”) denotes a monophonic audio signal.

Throughout this disclosure including in the claims, the expression“audio program” denotes a set of one or more audio channels andoptionally also associated metadata (e.g., metadata that describes adesired spatial audio presentation, and/or PIM, and/or SSM, and/or LPSM,and/or program boundary metadata).

Throughout this disclosure including in the claims, the expression“program boundary metadata” denotes metadata of an encoded audiobitstream, where the encoded audio bitstream is indicative of at leastone audio program (e.g., two or more audio programs), and the programboundary metadata is indicative of location in the bitstream of at leastone boundary (beginning and/or end) of at least one said audio program.For example, the program boundary metadata (of an encoded audiobitstream indicative of an audio program) may include metadataindicative of the location (e.g., the start of the “N” th frame of thebitstream, or the “M” th sample location of the bitstream's “N” thframe) of the beginning of the program, and additional metadataindicative of the location (e.g., the start of the “J” th frame of thebitstream, or the “K” th sample location of the bitstream's “J” thframe) of the program's end.

Throughout this disclosure including in the claims, the term “couples”or “coupled” is used to mean either a direct or indirect connection.Thus, if a first device couples to a second device, that connection maybe through a direct connection, or through an indirect connection viaother devices and connections.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

A typical stream of audio data includes both audio content (e.g., one ormore channels of audio content) and metadata indicative of at least onecharacteristic of the audio content. For example, in an AC-3 bitstreamthere are several audio metadata parameters that are specificallyintended for use in changing the sound of the program delivered to alistening environment. One of the metadata parameters is the DIALNORMparameter, which is intended to indicate the mean level of dialog in anaudio program, and is used to determine audio playback signal level.

During playback of a bitstream comprising a sequence of different audioprogram segments (each having a different DIALNORM parameter), an AC-3decoder uses the DIALNORM parameter of each segment to perform a type ofloudness processing in which it modifies the playback level or loudnessof such that the perceived loudness of the dialog of the sequence ofsegments is at a consistent level. Each encoded audio segment (item) ina sequence of encoded audio items would (in general) have a differentDIALNORM parameter, and the decoder would scale the level of each of theitems such that the playback level or loudness of the dialog for eachitem is the same or very similar, although this might requireapplication of different amounts of gain to different ones of the itemsduring playback.

DIALNORM typically is set by a user, and is not generated automatically,although there is a default DIALNORM value if no value is set by theuser. For example, a content creator may make loudness measurements witha device external to an AC-3 encoder and then transfer the result(indicative of the loudness of the spoken dialog of an audio program) tothe encoder to set the DIALNORM value. Thus, there is reliance on thecontent creator to set the DIALNORM parameter correctly.

There are several different reasons why the DIALNORM parameter in anAC-3 bitstream may be incorrect. First, each AC-3 encoder has a defaultDIALNORM value that is used during the generation of the bitstream if aDIALNORM value is not set by the content creator. This default value maybe substantially different than the actual dialog loudness level of theaudio. Second, even if a content creator measures loudness and sets theDIALNORM value accordingly, a loudness measurement algorithm or metermay have been used that does not conform to the recommended AC-3loudness measurement method, resulting in an incorrect DIALNORM value.Third, even if an AC-3 bitstream has been created with the DIALNORMvalue measured and set correctly by the content creator, it may havebeen changed to an incorrect value during transmission and/or storage ofthe bitstream. For example, it is not uncommon in television broadcastapplications for AC-3 bitstreams to be decoded, modified and thenre-encoded using incorrect DIALNORM metadata information. Thus, aDIALNORM value included in an AC-3 bitstream may be incorrect orinaccurate and therefore may have a negative impact on the quality ofthe listening experience.

Further, the DIALNORM parameter does not indicate the loudnessprocessing state of corresponding audio data (e.g. what type(s) ofloudness processing have been performed on the audio data). Loudnessprocessing state metadata (in the format in which it is provided in someembodiments of the present invention) is useful to facilitate adaptiveloudness processing of an audio bitstream and/or verification ofvalidity of the loudness processing state and loudness of the audiocontent, in a particularly efficient manner.

Although the present invention is not limited to use with an AC-3bitstream, an E-AC-3 bitstream, or a Dolby E bitstream, for convenienceit will be described in embodiments in which it generates, decodes, orotherwise processes such a bitstream.

An AC-3 encoded bitstream comprises metadata and one to six channels ofaudio content. The audio content is audio data that has been compressedusing perceptual audio coding. The metadata includes several audiometadata parameters that are intended for use in changing the sound of aprogram delivered to a listening environment.

Each frame of an AC-3 encoded audio bitstream contains audio content andmetadata for 1536 samples of digital audio. For a sampling rate of 48kHz, this represents 32 milliseconds of digital audio or a rate of 31.25frames per second of audio.

Each frame of an E-AC-3 encoded audio bitstream contains audio contentand metadata for 256, 512, 768 or 1536 samples of digital audio,depending on whether the frame contains one, two, three or six blocks ofaudio data respectively. For a sampling rate of 48 kHz, this represents5.333, 10.667, 16 or 32 milliseconds of digital audio respectively or arate of 189.9, 93.75, 62.5 or 31.25 frames per second of audiorespectively.

As indicated in FIG. 4, each AC-3 frame is divided into sections(segments), including: a Synchronization Information (SI) section whichcontains (as shown in FIG. 5) a synchronization word (SW) and the firstof two error correction words (CRC1); a Bitstream Information (BSI)section which contains most of the metadata; six Audio Blocks (AB0 toAB5) which contain data compressed audio content (and can also includemetadata); waste bit segments (W) (also known as “skip fields”) whichcontain any unused bits left over after the audio content is compressed;an Auxiliary (AUX) information section which may contain more metadata;and the second of two error correction words (CRC2).

As indicated in FIG. 7, each E-AC-3 frame is divided into sections(segments), including: a Synchronization Information (SI) section whichcontains (as shown in FIG. 5) a synchronization word (SW); a BitstreamInformation (BSI) section which contains most of the metadata; betweenone and six Audio Blocks (AB0 to AB5) which contain data compressedaudio content (and can also include metadata); waste bit segments (W)(also known as “skip fields”) which contain any unused bits left overafter the audio content is compressed (although only one waste bitsegment is shown, a different waste bit or skip field segment wouldtypically follow each audio block); an Auxiliary (AUX) informationsection which may contain more metadata; and an error correction word(CRC).

In an AC-3 (or E-AC-3) bitstream there are several audio metadataparameters that are specifically intended for use in changing the soundof the program delivered to a listening environment. One of the metadataparameters is the DIALNORM parameter, which is included in the BSIsegment.

As shown in FIG. 6, the BSI segment of an AC-3 frame includes a five-bitparameter (“DIALNORM”) indicating the DIALNORM value for the program. Afive-bit parameter (“DIALNORM2”) indicating the DIALNORM value for asecond audio program carried in the same AC-3 frame is included if theaudio coding mode (“acmod”) of the AC-3 frame is “0”, indicating that adual-mono or “1+1” channel configuration is in use.

The BSI segment also includes a flag (“addbsie”) indicating the presence(or absence) of additional bit stream information following the“addbsie” bit, a parameter (“addbsil”) indicating the length of anyadditional bit stream information following the “addbsil” value, and upto 64 bits of additional bit stream information (“addbsi”) following the“addbsil” value.

The BSI segment includes other metadata values not specifically shown inFIG. 6.

In accordance with a class of embodiments, an encoded audio bitstream isindicative of multiple substreams of audio content. In some cases, thesubstreams are indicative of audio content of a multichannel program,and each of the substreams is indicative of one or more of the program'schannels. In other cases, multiple substreams of an encoded audiobitstream are indicative of audio content of several audio programs,typically a “main” audio program (which may be a multichannel program)and at least one other audio program (e.g., a program which is acommentary on the main audio program).

An encoded audio bitstream which is indicative of at least one audioprogram necessarily includes at least one “independent” substream ofaudio content. The independent substream is indicative of at least onechannel of an audio program (e.g., the independent substream may beindicative of the five full range channels of a conventional 5.1 channelaudio program). Herein, this audio program is referred to as a “main”program.

In some classes of embodiments, an encoded audio bitstream is indicativeof two or more audio programs (a “main” program and at least one otheraudio program). In such cases, the bitstream includes two or moreindependent substreams: a first independent substream indicative of atleast one channel of the main program; and at least one otherindependent substream indicative of at least one channel of anotheraudio program (a program distinct from the main program).

Each independent bitstream can be independently decoded, and a decodercould operate to decode only a subset (not all) of the independentsubstreams of an encoded bitstream.

In a typical example of an encoded audio bitstream which is indicativeof two independent substreams, one of the independent substreams isindicative of standard format speaker channels of a multichannel mainprogram (e.g., Left, Right, Center, Left Surround, Right Surround fullrange speaker channels of a 5.1 channel main program), and the otherindependent substream is indicative of a monophonic audio commentary onthe main program (e.g., a director's commentary on a movie, where themain program is the movie's soundtrack). In another example of anencoded audio bitstream indicative of multiple independent substreams,one of the independent substreams is indicative of standard formatspeaker channels of a multichannel main program (e.g., a 5.1 channelmain program) including dialog in a first language (e.g., one of thespeaker channels of the main program may be indicative of the dialog),and each other independent substream is indicative of a monophonictranslation (into a different language) of the dialog.

Optionally, an encoded audio bitstream which is indicative of a mainprogram (and optionally also at least one other audio program) includesat least one “dependent” substream of audio content. Each dependentsubstream is associated with one independent substream of the bitstream,and is indicative of at least one additional channel of the program(e.g., the main program) whose content is indicated by the associatedindependent substream (i.e., the dependent substream is indicative of atleast one channel of a program which is not indicated by the associatedindependent substream, and the associated independent substream isindicative of at least one channel of the program).

In an example of an encoded bitstream which includes an independentsubstream (indicative of at least one channel of a main program), thebitstream also includes a dependent substream (associated with theindependent bitstream) which is indicative of one or more additionalspeaker channels of the main program. Such additional speaker channelsare additional to the main program channel(s) indicated by theindependent substream. For example, if the independent substream isindicative of standard format Left, Right, Center, Left Surround, RightSurround full range speaker channels of a 7.1 channel main program, thedependent substream may be indicative of the two other full rangespeaker channels of the main program.

In accordance with the E-AC-3 standard, an E-AC-3 bitstream must beindicative of at least one independent substream (e.g., a single AC-3bitstream), and may be indicative of up to eight independent substreams.Each independent substream of an E-AC-3 bitstream may be associated withup to eight dependent substreams.

An E-AC-3 bitstream includes metadata indicative of the bitstream'ssubstream structure. For example, a “chanmap” field in the BitstreamInformation (BSI) section of an E-AC-3 bitstream determines a channelmap for the program channels indicated by a dependent substream of thebitstream. However, metadata indicative of substream structure isconventionally included in an E-AC-3 bitstream in such a format that itis convenient for access and use (during decoding of the encoded E-AC-3bitstream) only by an E-AC-3 decoder; not for access and use afterdecoding (e.g., by a post-processor) or before decoding (e.g., by aprocessor configured to recognize the metadata). Also, there is a riskthat a decoder may incorrectly identify the substreams of a conventionalE-AC-3 encoded bitstream using the conventionally included metadata, andit had not been known until the present invention how to includesubstream structure metadata in an encoded bitstream (e.g., an encodedE-AC-3 bitstream) in such a format as to allow convenient and efficientdetection and correction of errors in substream identification duringdecoding of the bitstream.

An E-AC-3 bitstream may also include metadata regarding the audiocontent of an audio program. For example, an E-AC-3 bitstream indicativeof an audio program includes metadata indicative of minimum and maximumfrequencies to which spectral extension processing (and channel couplingencoding) has been employed to encode content of the program. However,such metadata is generally included in an E-AC-3 bitstream in such aformat that it is convenient for access and use (during decoding of theencoded E-AC-3 bitstream) only by an E-AC-3 decoder; not for access anduse after decoding (e.g., by a post-processor) or before decoding (e.g.,by a processor configured to recognize the metadata). Also, suchmetadata is not included in an E-AC-3 bitstream in a format that allowsconvenient and efficient error detection and error correction of theidentification of such metadata during decoding of the bitstream.

In accordance with typical embodiments of the invention, PIM and/or SSM(and optionally also other metadata, e.g., loudness processing statemetadata or “LPSM”) are embedded in one or more reserved fields (orslots) of metadata segments of an audio bitstream which also includesaudio data in other segments (audio data segments). Typically, at leastone segment of each frame of the bitstream includes PIM or SSM, and atleast one other segment of the frame includes corresponding audio data(i.e., audio data whose substream structure is indicated by the SSMand/or having at least one characteristic or property indicated by thePIM).

In a class of embodiments, each metadata segment is a data structure(sometimes referred to herein as a container) which may contain one ormore metadata payloads. Each payload includes a header including aspecific payload identifier (and payload configuration data) to providean unambiguous indication of the type of metadata present in thepayload. The order of payloads within the container is undefined, sothat payloads can be stored in any order and a parser must be able toparse the entire container to extract relevant payloads and ignorepayloads that are either not relevant or are unsupported. FIG. 8 (to bedescribed below) illustrates the structure of such a container andpayloads within the container.

Communicating metadata (e.g., SSM and/or PIM and/or LPSM) in an audiodata processing chain is particularly useful when two or more audioprocessing units need to work in tandem with one another throughout theprocessing chain (or content lifecycle). Without inclusion of metadatain an audio bitstream, severe media processing problems such as quality,level and spatial degradations may occur, for example, when two or moreaudio codecs are utilized in the chain and single-ended volume levelingis applied more than once during a bitstream path to a media consumingdevice (or a rendering point of the audio content of the bitstream).

Loudness processing state metadata (LPSM) embedded in an audio bitstreamin accordance with some embodiments of the invention may beauthenticated and validated, e.g., to enable loudness regulatoryentities to verify if a particular program's loudness is already withina specified range and that the corresponding audio data itself have notbeen modified (thereby ensuring compliance with applicable regulations).A loudness value included in a data block comprising the loudnessprocessing state metadata may be read out to verify this, instead ofcomputing the loudness again. In response to LPSM, a regulatory agencymay determine that corresponding audio content is in compliance (asindicated by the LPSM) with loudness statutory and/or regulatoryrequirements (e.g., the regulations promulgated under the CommercialAdvertisement Loudness Mitigation Act, also known as the “CALM” Act)without the need to compute loudness of the audio content.

FIG. 1 is a block diagram of an exemplary audio processing chain (anaudio data processing system), in which one or more of the elements ofthe system may be configured in accordance with an embodiment of thepresent invention. The system includes the followings elements, coupledtogether as shown: a pre-processing unit, an encoder, a signal analysisand metadata correction unit, a transcoder, a decoder, and apre-processing unit. In variations on the system shown, one or more ofthe elements are omitted, or additional audio data processing units areincluded.

In some implementations, the pre-processing unit of FIG. 1 is configuredto accept PCM (time-domain) samples comprising audio content as input,and to output processed PCM samples. The encoder may be configured toaccept the PCM samples as input and to output an encoded (e.g.,compressed) audio bitstream indicative of the audio content. The data ofthe bitstream that are indicative of the audio content are sometimesreferred to herein as “audio data.” If the encoder is configured inaccordance with a typical embodiment of the present invention, the audiobitstream output from the encoder includes PIM and/or SSM (andoptionally also loudness processing state metadata and/or othermetadata) as well as audio data.

The signal analysis and metadata correction unit of FIG. 1 may acceptone or more encoded audio bitstreams as input and determine (e.g.,validate) whether metadata (e.g., processing state metadata) in eachencoded audio bitstream is correct, by performing signal analysis (e.g.,using program boundary metadata in an encoded audio bitstream). If thesignal analysis and metadata correction unit finds that includedmetadata is invalid, it typically replaces the incorrect value(s) withthe correct value(s) obtained from signal analysis. Thus, each encodedaudio bitstream output from the signal analysis and metadata correctionunit may include corrected (or uncorrected) processing state metadata aswell as encoded audio data.

The transcoder of FIG. 1 may accept encoded audio bitstreams as input,and output modified (e.g., differently encoded) audio bitstreams inresponse (e.g., by decoding an input stream and re-encoding the decodedstream in a different encoding format). If the transcoder is configuredin accordance with a typical embodiment of the present invention, theaudio bitstream output from the transcoder includes SSM and/or PIM (andtypically also other metadata) as well as encoded audio data. Themetadata may have been included in the input bitstream.

The decoder of FIG. 1 may accept encoded (e.g., compressed) audiobitstreams as input, and output (in response) streams of decoded PCMaudio samples. If the decoder is configured in accordance with a typicalembodiment of the present invention, the output of the decoder intypical operation is or includes any of the following:

a stream of audio samples, and at least one corresponding stream of SSMand/or PIM (and typically also other metadata) extracted from an inputencoded bitstream; or

a stream of audio samples, and a corresponding stream of control bitsdetermined from SSM and/or PIM (and typically also other metadata, e.g.,LPSM) extracted from an input encoded bitstream; or

a stream of audio samples, without a corresponding stream of metadata orcontrol bits determined from metadata. In this last case, the decodermay extract metadata from the input encoded bitstream and perform itleast one operation on the extracted metadata (e.g., validation), eventhough it does not output the extracted metadata or control bitsdetermined therefrom.

By configuring the post-processing unit of FIG. 1 in accordance with atypical embodiment of the present invention, the post-processing unit isconfigured to accept a stream of decoded PCM audio samples, and toperform post processing thereon (e.g., volume leveling of the audiocontent) using SSM and/or PIM (and typically also other metadata, e.g.,LPSM) received with the samples, or control bits determined by thedecoder from metadata received with the samples. The post-processingunit is typically also configured to render the post-processed audiocontent for playback by one or more speakers.

Typical embodiments of the present invention provide an enhanced audioprocessing chain in which audio processing units (e.g., encoders,decoders, transcoders, and pre- and post-processing units) adapt theirrespective processing to be applied to audio data according to acontemporaneous state of the media data as indicated by metadatarespectively received by the audio processing units.

The audio data input to any audio processing unit of the FIG. 1 system(e.g., the encoder or transcoder of FIG. 1) may include SSM and/or PIM(and optionally also other metadata) as well as audio data (e.g.,encoded audio data). This metadata may have been included in the inputaudio by another element of the FIG. 1 system (or another source, notshown in FIG. 1) in accordance with an embodiment of the presentinvention. The processing unit which receives the input audio (withmetadata) may be configured to perform it least one operation on themetadata (e.g., validation) or in response to the metadata (e.g.,adaptive processing of the input audio), and typically also to includein its output audio the metadata, a processed version of the metadata,or control bits determined from the metadata.

A typical embodiment of the inventive audio processing unit (or audioprocessor) is configured to perform adaptive processing of audio databased on the state of the audio data as indicated by metadatacorresponding to the audio data. In some embodiments, the adaptiveprocessing is (or includes) loudness processing (if the metadataindicates that the loudness processing, or processing similar thereto,has not already been performed on the audio data, but is not (and doesnot include) loudness processing (if the metadata indicates that suchloudness processing, or processing similar thereto, has already beenperformed on the audio data). In some embodiments, the adaptiveprocessing is or includes metadata validation (e.g., performed in ametadata validation sub-unit) to ensure the audio processing unitperforms other adaptive processing of the audio data based on the stateof the audio data as indicated by the metadata. In some embodiments, thevalidation determines reliability of the metadata associated with (e.g.,included in a bitstream with) the audio data. For example, if themetadata is validated to be reliable, then results from a type ofpreviously performed audio processing may be re-used and new performanceof the same type of audio processing may be avoided. On the other hand,if the metadata is found to have been tampered with (or otherwiseunreliable), then the type of media processing purportedly previouslyperformed (as indicated by the unreliable metadata) may be repeated bythe audio processing unit, and/or other processing may be performed bythe audio processing unit on the metadata and/or the audio data. Theaudio processing unit may also be configured to signal to other audioprocessing units downstream in an enhanced media processing chain thatmetadata (e.g., present in a media bitstream) is valid, if the unitdetermines that the metadata is valid (e.g., based on a match of acryptographic value extracted and a reference cryptographic value).

FIG. 2 is a block diagram of an encoder (100) which is an embodiment ofthe inventive audio processing unit. Any of the components or elementsof encoder 100 may be implemented as one or more processes and/or one ormore circuits (e.g., ASICs, FPGAs, or other integrated circuits), inhardware, software, or a combination of hardware and software. Encoder100 comprises frame buffer 110, parser 111, decoder 101, audio statevalidator 102, loudness processing stage 103, audio stream selectionstage 104, encoder 105, stuffer/formatter stage 107, metadata generationstage 106, dialog loudness measurement subsystem 108, and frame buffer109, connected as shown. Typically also, encoder 100 includes otherprocessing elements (not shown).

Encoder 100 (which is a transcoder) is configured to convert an inputaudio bitstream (which, for example, may be one of an AC-3 bitstream, anE-AC-3 bitstream, or a Dolby E bitstream) to an encoded output audiobitstream (which, for example, may be another one of an AC-3 bitstream,an E-AC-3 bitstream, or a Dolby E bitstream) including by performingadaptive and automated loudness processing using loudness processingstate metadata included in the input bitstream. For example, encoder 100may be configured to convert an input Dolby E bitstream (a formattypically used in production and broadcast facilities but not inconsumer devices which receive audio programs which have been broadcastthereto) to an encoded output audio bitstream (suitable for broadcastingto consumer devices) in AC-3 or E-AC-3 format.

The system of FIG. 2 also includes encoded audio delivery subsystem 150(which stores and/or delivers the encoded bitstreams output from encoder100) and decoder 152. An encoded audio bitstream output from encoder 100may be stored by subsystem 150 (e.g., in the form of a DVD or Blu raydisc), or transmitted by subsystem 150 (which may implement atransmission link or network), or may be both stored and transmitted bysubsystem 150. Decoder 152 is configured to decode an encoded audiobitstream (generated by encoder 100) which it receives via subsystem150, including by extracting metadata (PIM and/or SSM, and optionallyalso loudness processing state metadata and/or other metadata) from eachframe of the bitstream (and optionally also extracting program boundarymetadata from the bitstream), and generating decoded audio data.Typically, decoder 152 is configured to perform adaptive processing onthe decoded audio data using PIM and/or SSM, and/or LPSM (and optionallyalso program boundary metadata), and/or to forward the decoded audiodata and metadata to a post-processor configured to perform adaptiveprocessing on the decoded audio data using the metadata. Typically,decoder 152 includes a buffer which stores (e.g., in a non-transitorymanner) the encoded audio bitstream received from subsystem 150.

Various implementations of encoder 100 and decoder 152 are configured toperform different embodiments of the inventive method. Frame buffer 110is a buffer memory coupled to receive an encoded input audio bitstream.In operation, buffer 110 stores (e.g., in a non-transitory manner) atleast one frame of the encoded audio bitstream, and a sequence of theframes of the encoded audio bitstream is asserted from buffer 110 toparser 111.

Parser 111 is coupled and configured to extract PIM and/or SSM, andloudness processing state metadata (LPSM), and optionally also programboundary metadata (and/or other metadata) from each frame of the encodedinput audio in which such metadata is included, to assert at least theLPSM (and optionally also program boundary metadata and/or othermetadata) to audio state validator 102, loudness processing stage 103,stage 106 and subsystem 108, to extract audio data from the encodedinput audio, and to assert the audio data to decoder 101. Decoder 101 ofencoder 100 is configured to decode the audio data to generate decodedaudio data, and to assert the decoded audio data to loudness processingstage 103, audio stream selection stage 104, subsystem 108, andtypically also to state validator 102.

State validator 102 is configured to authenticate and validate the LPSM(and optionally other metadata) asserted thereto. In some embodiments,the LPSM is (or is included in) a data block that has been included inthe input bitstream (e.g., in accordance with an embodiment of thepresent invention). The block may comprise a cryptographic hash (ahash-based message authentication code or “HMAC”) for processing theLPSM (and optionally also other metadata) and/or the underlying audiodata (provided from decoder 101 to validator 102). The data block may bedigitally signed in these embodiments, so that a downstream audioprocessing unit may relatively easily authenticate and validate theprocessing state metadata.

For example, the HMAC is used to generate a digest, and the protectionvalue(s) included in the inventive bitstream may include the digest. Thedigest may be generated as follows for an AC-3 frame:

1. After AC-3 data and LPSM are encoded, frame data bytes (concatenatedframe_data #1 and frame_data #2) and the LPSM data bytes are used asinput for the hashing-function HMAC. Other data, which may be presentinside an auxdata field, are not taken into consideration forcalculating the digest. Such other data may be bytes neither belongingto the AC-3 data nor to the LSPSM data. Protection bits included in LPSMmay not be considered for calculating the HMAC digest.2. After the digest is calculated, it is written into the bitstream in afield reserved for protection bits.3. The last step of the generation of the complete AC-3 frame is thecalculation of the CRC-check. This is written at the very end of theframe and all data belonging to this frame is taken into consideration,including the LPSM bits.

Other cryptographic methods including but not limited to any of one ormore non-HMAC cryptographic methods may be used for validation of LPSMand/or other metadata (e.g., in validator 102) to ensure securetransmission and receipt of the metadata and/or the underlying audiodata. For example, validation (using such a cryptographic method) can beperformed in each audio processing unit which receives an embodiment ofthe inventive audio bitstream to determine whether metadata andcorresponding audio data included in the bitstream have undergone(and/or have resulted from) specific processing (as indicated by themetadata) and have not been modified after performance of such specificprocessing.

State validator 102 asserts control data to audio stream selection stage104, metadata generator 106, and dialog loudness measurement subsystem108, to indicate the results of the validation operation. In response tothe control data, stage 104 may select (and pass through to encoder 105)either:

the adaptively processed output of loudness processing stage 103 (e.g.,when LPSM indicate that the audio data output from decoder 101 have notundergone a specific type of loudness processing, and the control bitsfrom validator 102 indicate that the LPSM are valid); or

the audio data output from decoder 101 (e.g., when LPSM indicate thatthe audio data output from decoder 101 have already undergone thespecific type of loudness processing that would be performed by stage103, and the control bits from validator 102 indicate that the LPSM arevalid).

Stage 103 of encoder 100 is configured to perform adaptive loudnessprocessing on the decoded audio data output from decoder 101, based onone or more audio data characteristics indicated by LPSM extracted bydecoder 101. Stage 103 may be an adaptive transform-domain real timeloudness and dynamic range control processor. Stage 103 may receive userinput (e.g., user target loudness/dynamic range values or dialnormvalues), or other metadata input (e.g., one or more types of third partydata, tracking information, identifiers, proprietary or standardinformation, user annotation data, user preference data, etc.) and/orother input (e.g., from a fingerprinting process), and use such input toprocess the decoded audio data output from decoder 101. Stage 103 mayperform adaptive loudness processing on decoded audio data (output fromdecoder 101) indicative of a single audio program (as indicated byprogram boundary metadata extracted by parser 111), and may reset theloudness processing in response to receiving decoded audio data (outputfrom decoder 101) indicative of a different audio program as indicatedby program boundary metadata extracted by parser 111.

Dialog loudness measurement subsystem 108 may operate to determineloudness of segments of the decoded audio (from decoder 101) which areindicative of dialog (or other speech), e.g., using LPSM (and/or othermetadata) extracted by decoder 101, when the control bits from validator102 indicate that the LPSM are invalid. Operation of dialog loudnessmeasurement subsystem 108 may be disabled when the LPSM indicatepreviously determined loudness of dialog (or other speech) segments ofthe decoded audio (from decoder 101) when the control bits fromvalidator 102 indicate that the LPSM are valid. Subsystem 108 mayperform a loudness measurement on decoded audio data indicative of asingle audio program (as indicated by program boundary metadataextracted by parser 111), and may reset the measurement in response toreceiving decoded audio data indicative of a different audio program asindicated by such program boundary metadata.

Useful tools (e.g., the Dolby LM100 loudness meter) exist for measuringthe level of dialog in audio content conveniently and easily. Someembodiments of the inventive APU (e.g., stage 108 of encoder 100) areimplemented to include (or to perform the functions of) such a tool tomeasure the mean dialog loudness of audio content of an audio bitstream(e.g., a decoded AC-3 bitstream asserted to stage 108 from decoder 101of encoder 100).

If stage 108 is implemented to measure the true mean dialog loudness ofaudio data, the measurement may include a step of isolating segments ofthe audio content that predominantly contain speech. The audio segmentsthat predominantly are speech are then processed in accordance with aloudness measurement algorithm. For audio data decoded from an AC-3bitstream, this algorithm may be a standard K-weighted loudness measure(in accordance with the international standard ITU-R BS.1770).Alternatively, other loudness measures may be used (e.g., those based onpsychoacoustic models of loudness).

The isolation of speech segments is not essential to measure the meandialog loudness of audio data. However, it improves the accuracy of themeasure and typically provides more satisfactory results from alistener's perspective. Because not all audio content contains dialog(speech), the loudness measure of the whole audio content may provide asufficient approximation of the dialog level of the audio, had speechbeen present.

Metadata generator 106 generates (and/or passes through to stage 107)metadata to be included by stage 107 in the encoded bitstream to beoutput from encoder 100. Metadata generator 106 may pass through tostage 107 the LPSM (and optionally also LIM and/or PIM and/or programboundary metadata and/or other metadata) extracted by encoder 101 and/orparser 111 (e.g., when control bits from validator 102 indicate that theLPSM and/or other metadata are valid), or generate new LIM and/or PIMand/or LPSM and/or program boundary metadata and/or other metadata andassert the new metadata to stage 107 (e.g., when control bits fromvalidator 102 indicate that metadata extracted by decoder 101 areinvalid), or it may assert to stage 107 a combination of metadataextracted by decoder 101 and/or parser 111 and newly generated metadata.Metadata generator 106 may include loudness data generated by subsystem108, and at least one value indicative of the type of loudnessprocessing performed by subsystem 108, in LPSM which it asserts to stage107 for inclusion in the encoded bitstream to be output from encoder100.

Metadata generator 106 may generate protection bits (which may consistof or include a hash-based message authentication code or “HMAC”) usefulfor at least one of decryption, authentication, or validation of theLPSM (and optionally also other metadata) to be included in the encodedbitstream and/or the underlying audio data to be included in the encodedbitstream. Metadata generator 106 may provide such protection bits tostage 107 for inclusion in the encoded bitstream.

In typical operation, dialog loudness measurement subsystem 108processes the audio data output from decoder 101 to generate in responsethereto loudness values (e.g., gated and ungated dialog loudness values)and dynamic range values. In response to these values, metadatagenerator 106 may generate loudness processing state metadata (LPSM) forinclusion (by stuffer/formatter 107) into the encoded bitstream to beoutput from encoder 100.

Additionally, optionally, or alternatively, subsystems of 106 and/or 108of encoder 100 may perform additional analysis of the audio data togenerate metadata indicative of at least one characteristic of the audiodata for inclusion in the encoded bitstream to be output from stage 107.

Encoder 105 encodes (e.g., by performing compression thereon) the audiodata output from selection stage 104, and asserts the encoded audio tostage 107 for inclusion in the encoded bitstream to be output from stage107.

Stage 107 multiplexes the encoded audio from encoder 105 and themetadata (including PIM and/or SSM) from generator 106 to generate theencoded bitstream to be output from stage 107, preferably so that theencoded bitstream has format as specified by a preferred embodiment ofthe present invention.

Frame buffer 109 is a buffer memory which stores (e.g., in anon-transitory manner) at least one frame of the encoded audio bitstreamoutput from stage 107, and a sequence of the frames of the encoded audiobitstream is then asserted from buffer 109 as output from encoder 100 todelivery system 150.

LPSM generated by metadata generator 106 and included in the encodedbitstream by stage 107 is typically indicative of the loudnessprocessing state of corresponding audio data (e.g., what type(s) ofloudness processing have been performed on the audio data) and loudness(e.g., measured dialog loudness, gated and/or ungated loudness, and/ordynamic range) of the corresponding audio data.

Herein, “gating” of loudness and/or level measurements performed onaudio data refers to a specific level or loudness threshold wherecomputed value(s) that exceed the threshold are included in the finalmeasurement (e.g., ignoring short term loudness values below −60 dBFS inthe final measured values). Gating on an absolute value refers to afixed level or loudness, whereas gating on a relative value refers to avalue that is dependent on a current “ungated” measurement value.

In some implementations of encoder 100, the encoded bitstream bufferedin memory 109 (and output to delivery system 150) is an AC-3 bitstreamor an E-AC-3 bitstream, and comprises audio data segments (e.g., theAB0-AB5 segments of the frame shown in FIG. 4) and metadata segments,where the audio data segments are indicative of audio data, and each ofat least some of the metadata segments includes PIM and/or SSM (andoptionally also other metadata). Stage 107 inserts metadata segments(including metadata) into the bitstream in the following format. Each ofthe metadata segments which includes PIM and/or SSM is included in awaste bit segment of the bitstream (e.g., a waste bit segment “W” asshown in FIG. 4 or FIG. 7), or an “addbsi” field of the BitstreamInformation (“BSI”) segment of a frame of the bitstream, or in anauxdata field (e.g., the AUX segment shown in FIG. 4 or FIG. 7) at theend of a frame of the bitstream. A frame of the bitstream may includeone or two metadata segments, each of which includes metadata, and ifthe frame includes two metadata segments, one may be present in theaddbsi field of the frame and the other in the AUX field of the frame.

In some embodiments, each metadata segment (sometimes referred to hereinas a “container”) inserted by stage 107 has a format which includes ametadata segment header (and optionally also other mandatory or “core”elements), and one or more metadata payloads following the metadatasegment header. SIM, if present, is included in one of the metadatapayloads (identified by a payload header, and typically having format ofa first type). PIM, if present, is included in another one of themetadata payloads (identified by a payload header and typically havingformat of a second type). Similarly, each other type of metadata (ifpresent) is included in another one of the metadata payloads (identifiedby a payload header and typically having format specific to the type ofmetadata). The exemplary format allows convenient access to the SSM,PIM, and other metadata at times other than during decoding (e.g., by apost-processor following decoding, or by a processor configured torecognize the metadata without performing full decoding on the encodedbitstream), and allows convenient and efficient error detection andcorrection (e.g., of substream identification) during decoding of thebitstream. For example, without access to SSM in the exemplary format, adecoder might incorrectly identify the correct number of substreamsassociated with a program. One metadata payload in a metadata segmentmay include SSM, another metadata payload in the metadata segment mayinclude PIM, and optionally also at least one other metadata payload inthe metadata segment may include other metadata (e.g., loudnessprocessing state metadata or “LPSM”).

In some embodiments, a substream structure metadata (SSM) payloadincluded (by stage 107) in a frame of an encoded bitstream (e.g., anE-AC-3 bitstream indicative of at least one audio program) includes SSMin the following format:

a payload header, typically including at least one identification value(e.g., a 2-bit value indicative of SSM format version, and optionallyalso length, period, count, and substream association values); and afterthe header:

independent substream metadata indicative of the number of independentsubstreams of the program indicated by the bitstream; and

dependent substream metadata indicative of whether each independentsubstream of the program has at least one associated dependent substream(i.e., whether at least one dependent substream is associated with saideach independent substream), and if so the number of dependentsubstreams associated with each independent substream of the program.

It is contemplated that an independent substream of an encoded bitstreammay be indicative of a set of speaker channels of an audio program(e.g., the speaker channels of a 5.1 speaker channel audio program), andthat each of one or more dependent substreams (associated with theindependent substream, as indicated by dependent substream metadata) maybe indicative of an object channel of the program. Typically, however,an independent substream of an encoded bitstream is indicative of a setof speaker channels of a program, and each dependent substreamassociated with the independent substream (as indicated by dependentsubstream metadata) is indicative of at least one additional speakerchannel of the program.

In some embodiments, a program information metadata (PIM) payloadincluded (by stage 107) in a frame of an encoded bitstream (e.g., anE-AC-3 bitstream indicative of at least one audio program) has thefollowing format:

a payload header, typically including at least one identification value(e.g., a value indicative of PIM format version, and optionally alsolength, period, count, and substream association values); and

after the header, PIM in the following format:

active channel metadata indicative of each silent channel and eachnon-silent channel of an audio program (i.e., which channel(s) of theprogram contain audio information, and which (if any) contain onlysilence (typically for the duration of the frame)). In embodiments inwhich the encoded bitstream is an AC-3 or E-AC-3 bitstream, the activechannel metadata in a frame of the bitstream may be used in conjunctionwith additional metadata of the bitstream (e.g., the audio coding mode(“acmod”) field of the frame, and, if present, the chanmap field in theframe or associated dependent substream frame(s)) to determine whichchannel(s) of the program contain audio information and which containsilence. The “acmod” field of an AC-3 or E-AC-3 frame indicates thenumber of full range channels of an audio program indicated by audiocontent of the frame (e.g., whether the program is a 1.0 channelmonophonic program, a 2.0 channel stereo program, or a programcomprising L, R, C, Ls, Rs full range channels), or that the frame isindicative of two independent 1.0 channel monophonic programs. A“chanmap” field of an E-AC-3 bitstream indicates a channel map for adependent substream indicated by the bitstream. Active channel metadatamay be useful for implementing upmixing (in a post-processor) downstreamof a decoder, for example to add audio to channels that contain silenceat the output of the decoder;

downmix processing state metadata indicative of whether the program wasdownmixed (prior to or during encoding), and if so, the type ofdownmixing that was applied. Downmix processing state metadata may beuseful for implementing upmixing (in a post-processor) downstream of adecoder, for example to upmix the audio content of the program usingparameters that most closely match a type of downmixing that wasapplied. In embodiments in which the encoded bitstream is an AC-3 orE-AC-3 bitstream, the downmix processing state metadata may be used inconjunction with the audio coding mode (“acmod”) field of the frame todetermine the type of downmixing (if any) applied to the channel(s) ofthe program;

upmix processing state metadata indicative of whether the program wasupmixed (e.g., from a smaller number of channels) prior to or duringencoding, and if so, the type of upmixing that was applied. Upmixprocessing state metadata may be useful for implementing downmixing (ina post-processor) downstream of a decoder, for example to downmix theaudio content of the program in a manner that is compatible with a typeof upmixing (e.g., Dolby Pro Logic, or Dolby Pro Logic II Movie Mode, orDolby Pro Logic II Music Mode, or Dolby Professional Upmixer) that wasapplied to the program. In embodiments in which the encoded bitstream isan E-AC-3 bitstream, the upmix processing state metadata may be used inconjunction with other metadata (e.g., the value of a “strmtyp” field ofthe frame) to determine the type of upmixing (if any) applied to thechannel(s) of the program. The value of the “strmtyp” field (in the BSIsegment of a frame of an E-AC-3 bitstream) indicates whether audiocontent of the frame belongs to an independent stream (which determinesa program) or an independent substream (of a program which includes oris associated with multiple substreams) and thus may be decodedindependently of any other substream indicated by the E-AC-3 bitstream,or whether audio content of the frame belongs to a dependent substream(of a program which includes or is associated with multiple substreams)and thus must be decoded in conjunction with an independent substreamwith which it is associated; and preprocessing state metadata indicativeof whether preprocessing was performed on audio content of the frame(before encoding of the audio content to generated the encodedbitstream), and if so the type of preprocessing that was performed.

In some implementations, the preprocessing state metadata is indicativeof:

whether surround attenuation was applied (e.g., whether surroundchannels of the audio program were attenuated by 3 dB prior toencoding),

whether 90 degree phase shift applied (e.g., to surround channels Ls andRs channels of the audio program prior to encoding),

whether a low-pass filter was applied to an LFE channel of the audioprogram prior to encoding,

whether level of an LFE channel of the program was monitored duringproduction and if so the monitored level of the LFE channel relative tolevel of the full range audio channels of the program,

whether dynamic range compression should be performed (e.g., in thedecoder) on each block of decoded audio content of the program and if sothe type (and/or parameters) of dynamic range compression to beperformed (e.g., this type of preprocessing state metadata may beindicative of which of the following compression profile types wasassumed by the encoder to generate dynamic range compression controlvalues that are included in the encoded bitstream: Film Standard, FilmLight, Music Standard, Music Light, or Speech. Alternatively, this typeof preprocessing state metadata may indicate that heavy dynamic rangecompression (“compr” compression) should be performed on each frame ofdecoded audio content of the program in a manner determined by dynamicrange compression control values that are included in the encodedbitstream),

whether spectral extension processing and/or channel coupling encodingwas employed to encode specific frequency ranges of content of theprogram and if so the minimum and maximum frequencies of the frequencycomponents of the content on which spectral extension encoding wasperformed, and the minimum and maximum frequencies of frequencycomponents of the content on which channel coupling encoding wasperformed. This type of preprocessing state metadata information may beuseful to perform equalization (in a post-processor) downstream of adecoder. Both channel coupling and spectral extension information arealso useful for optimizing quality during transcode operations andapplications. For example, an encoder may optimize its behavior(including the adaptation of pre-processing steps such as headphonevirtualization, up mixing, etc.) based on the state of parameters, suchas spectral extension and channel coupling information. Moreover, theencoder may would adapt its coupling and spectral extension parametersdynamically to match and/or to optimal values based on the state of theinbound (and authenticated) metadata, and

whether dialog enhancement adjustment range data is included in theencoded bitstream, and if so the range of adjustment available duringperformance of dialog enhancement processing (e.g., in a post-processordownstream of a decoder) to adjust the level of dialog content relativeto the level of non-dialog content in the audio program.

In some implementations, additional preprocessing state metadata (e.g.,metadata indicative of headphone-related parameters) is included (bystage 107) in a PIM payload of an encoded bitstream to be output fromencoder 100.

In some embodiments, an LPSM payload included (by stage 107) in a frameof an encoded bitstream (e.g., an E-AC-3 bitstream indicative of atleast one audio program) includes LPSM in the following format:

a header (typically including a syncword identifying the start of theLPSM payload, followed by at least one identification value, e.g., theLPSM format version, length, period, count, and substream associationvalues indicated in Table 2 below); and

after the header,

at least one dialog indication value (e.g., parameter “Dialogchannel(s)” of Table 2) indicating whether corresponding audio dataindicates dialog or does not indicate dialog (e.g., which channels ofcorresponding audio data indicate dialog);

at least one loudness regulation compliance value (e.g., parameter“Loudness Regulation Type” of Table 2) indicating whether correspondingaudio data complies with an indicated set of loudness regulations;

at least one loudness processing value (e.g., one or more of parameters“Dialog gated Loudness Correction flag,” “Loudness Correction Type,” ofTable 2) indicating at least one type of loudness processing which hasbeen performed on the corresponding audio data; and

at least one loudness value (e.g., one or more of parameters “ITURelative Gated Loudness,” “ITU Speech Gated Loudness,” “ITU (EBU 3341)Short-term 3 s Loudness,” and “True Peak” of Table 2) indicating atleast one loudness (e.g., peak or average loudness) characteristic ofthe corresponding audio data.

In some embodiments, each metadata segment which contains PIM and/or SSM(and optionally also other metadata) contains a metadata segment header(and optionally also additional core elements), and after the metadatasegment header (or the metadata segment header and other core elements)at least one metadata payload segment having the following format:

a payload header, typically including at least one identification value(e.g., SSM or PIM format version, length, period, count, and substreamassociation values), and

after the payload header, the SSM or PIM (or metadata of another type).

In some implementations, each of the metadata segments (sometimesreferred to herein as “metadata containers” or “containers”) inserted bystage 107 into a waste bit/skip field segment (or an “addbsi” field oran auxdata field) of a frame of the bitstream has the following format:

a metadata segment header (typically including a syncword identifyingthe start of the metadata segment, followed by identification values,e.g., version, length, period, expanded element count, and substreamassociation values as indicated in Table 1 below); and

after the metadata segment header, at least one protection value (e.g.,the HMAC digest and Audio Fingerprint values of Table 1) useful for atleast one of decryption, authentication, or validation of at least oneof metadata of the metadata segment or the corresponding audio data);and

also after the metadata segment header, metadata payload identification(“ID”) and payload configuration values which identify the type ofmetadata in each following metadata payload and indicate at least oneaspect of configuration (e.g., size) of each such payload.

Each metadata payload follows the corresponding payload ID and payloadconfiguration values.

In some embodiments, each of the metadata segments in the waste bitsegment (or auxdata field or “addbsi” field) of a frame has three levelsof structure:

a high level structure (e.g., a metadata segment header), including aflag indicating whether the waste bit (or auxdata or addbsi) fieldincludes metadata, at least one ID value indicating what type(s) ofmetadata are present, and typically also a value indicating how manybits of metadata (e.g., of each type) are present (if metadata ispresent). One type of metadata that could be present is PIM, anothertype of metadata that could be present is SSM, and other types ofmetadata that could be present are LPSM, and/or program boundarymetadata, and/or media research metadata;

an intermediate level structure, comprising data associated with eachidentified type of metadata (e.g., metadata payload header, protectionvalues, and payload ID and payload configuration values for eachidentified type of metadata); and

a low level structure, comprising a metadata payload for each identifiedtype of metadata (e.g., a sequence of PIM values, if PIM is identifiedas being present, and/or metadata values of another type (e.g., SSM orLPSM), if this other type of metadata is identified as being present).

The data values in such a three level structure can be nested. Forexample, the protection value(s) for each payload (e.g., each PIM, orSSM, or other metadata payload) identified by the high and intermediatelevel structures can be included after the payload (and thus after thepayload's metadata payload header), or the protection value(s) for allmetadata payloads identified by the high and intermediate levelstructures can be included after the final metadata payload in themetadata segment (and thus after the metadata payload headers of all thepayloads of the metadata segment).

In one example (to be described with reference to the metadata segmentor “container” of FIG. 8), a metadata segment header identifies fourmetadata payloads. As shown in FIG. 8, the metadata segment headercomprises a container sync word (identified as “container sync”) andversion and key ID values. The metadata segment header is followed bythe four metadata payloads and protection bits. Payload ID and payloadconfiguration (e.g., payload size) values for the first payload (e.g., aPIM payload) follow the metadata segment header, the first payloaditself follows the ID and configuration values, payload ID and payloadconfiguration (e.g., payload size) values for the second payload (e.g.,an SSM payload) follow the first payload, the second payload itselffollows these ID and configuration values, payload ID and payloadconfiguration (e.g., payload size) values for the third payload (e.g.,an LPSM payload) follow the second payload, the third payload itselffollows these ID and configuration values, payload ID and payloadconfiguration (e.g., payload size) values for the fourth payload, followthe third payload, the fourth payload itself follows these ID andconfiguration values, and protection value(s) (identified as “ProtectionData” in FIG. 8) for all or some of the payloads (or for the high andintermediate level structure and all or some of the payloads) follow thelast payload.

In some embodiments, if decoder 101 receives an audio bitstreamgenerated in accordance with an embodiment of the invention with acryptographic hash, the decoder is configured to parse and retrieve thecryptographic hash from a data block determined from the bitstream,where said block includes metadata. Validator 102 may use thecryptographic hash to validate the received bitstream and/or associatedmetadata. For example, if validator 102 finds the metadata to be validbased on a match between a reference cryptographic hash and thecryptographic hash retrieved from the data block, then it may disableoperation of processor 103 on the corresponding audio data and causeselection stage 104 to pass through (unchanged) the audio data.Additionally, optionally, or alternatively, other types of cryptographictechniques may be used in place of a method based on a cryptographichash.

Encoder 100 of FIG. 2 may determine (in response to LPSM, and optionallyalso program boundary metadata, extracted by decoder 101) that apost/pre-processing unit has performed a type of loudness processing onthe audio data to be encoded (in elements 105, 106, and 107) and hencemay create (in generator 106) loudness processing state metadata thatincludes the specific parameters used in and/or derived from thepreviously performed loudness processing. In some implementations,encoder 100 may create (and include in the encoded bitstream outputtherefrom) metadata indicative of processing history on the audiocontent so long as the encoder is aware of the types of processing thathave been performed on the audio content.

FIG. 3 is a block diagram of a decoder (200) which is an embodiment ofthe inventive audio processing unit, and of a post-processor (300)coupled thereto. Post-processor (300) is also an embodiment of theinventive audio processing unit. Any of the components or elements ofdecoder 200 and post-processor 300 may be implemented as one or moreprocesses and/or one or more circuits (e.g., ASICs, FPGAs, or otherintegrated circuits), in hardware, software, or a combination ofhardware and software. Decoder 200 comprises frame buffer 201, parser205, audio decoder 202, audio state validation stage (validator) 203,and control bit generation stage 204, connected as shown. Typicallyalso, decoder 200 includes other processing elements (not shown).

Frame buffer 201 (a buffer memory) stores (e.g., in a non-transitorymanner) at least one frame of the encoded audio bitstream received bydecoder 200. A sequence of the frames of the encoded audio bitstream isasserted from buffer 201 to parser 205.

Parser 205 is coupled and configured to extract PIM and/or SSM (andoptionally also other metadata, e.g., LPSM) from each frame of theencoded input audio, to assert at least some of the metadata (e.g., LPSMand program boundary metadata if any is extracted, and/or PIM and/orSSM) to audio state validator 203 and stage 204, to assert the extractedmetadata as output (e.g., to post-processor 300), to extract audio datafrom the encoded input audio, and to assert the extracted audio data todecoder 202.

The encoded audio bitstream input to decoder 200 may be one of an AC-3bitstream, an E-AC-3 bitstream, or a Dolby E bitstream.

The system of FIG. 3 also includes post-processor 300. Post-processor300 comprises frame buffer 301 and other processing elements (not shown)including at least one processing element coupled to buffer 301. Framebuffer 301 stores (e.g., in a non-transitory manner) at least one frameof the decoded audio bitstream received by post-processor 300 fromdecoder 200. Processing elements of post-processor 300 are coupled andconfigured to receive and adaptively process a sequence of the frames ofthe decoded audio bitstream output from buffer 301, using metadataoutput from decoder 200 and/or control bits output from stage 204 ofdecoder 200. Typically, post-processor 300 is configured to performadaptive processing on the decoded audio data using metadata fromdecoder 200 (e.g., adaptive loudness processing on the decoded audiodata using LPSM values and optionally also program boundary metadata,where the adaptive processing may be based on loudness processing state,and/or one or more audio data characteristics, indicated by LPSM foraudio data indicative of a single audio program).

Various implementations of decoder 200 and post-processor 300 areconfigured to perform different embodiments of the inventive method.

Audio decoder 202 of decoder 200 is configured to decode the audio dataextracted by parser 205 to generate decoded audio data, and to assertthe decoded audio data as output (e.g., to post-processor 300).

State validator 203 is configured to authenticate and validate themetadata asserted thereto. In some embodiments, the metadata is (or isincluded in) a data block that has been included in the input bitstream(e.g., in accordance with an embodiment of the present invention). Theblock may comprise a cryptographic hash (a hash-based messageauthentication code or “HMAC”) for processing the metadata and/or theunderlying audio data (provided from parser 205 and/or decoder 202 tovalidator 203). The data block may be digitally signed in theseembodiments, so that a downstream audio processing unit may relativelyeasily authenticate and validate the processing state metadata.

Other cryptographic methods including but not limited to any of one ormore non-HMAC cryptographic methods may be used for validation ofmetadata (e.g., in validator 203) to ensure secure transmission andreceipt of the metadata and/or the underlying audio data. For example,validation (using such a cryptographic method) can be performed in eachaudio processing unit which receives an embodiment of the inventiveaudio bitstream to determine whether loudness processing state metadataand corresponding audio data included in the bitstream have undergone(and/or have resulted from) specific loudness processing (as indicatedby the metadata) and have not been modified after performance of suchspecific loudness processing.

State validator 203 asserts control data to control bit generator 204,and/or asserts the control data as output (e.g., to post-processor 300),to indicate the results of the validation operation. In response to thecontrol data (and optionally also other metadata extracted from theinput bitstream), stage 204 may generate (and assert to post-processor300) either:

control bits indicating that decoded audio data output from decoder 202have undergone a specific type of loudness processing (when LPSMindicate that the audio data output from decoder 202 have undergone thespecific type of loudness processing, and the control bits fromvalidator 203 indicate that the LPSM are valid); or

control bits indicating that decoded audio data output from decoder 202should undergo a specific type of loudness processing (e.g., when LPSMindicate that the audio data output from decoder 202 have not undergonethe specific type of loudness processing, or when the LPSM indicate thatthe audio data output from decoder 202 have undergone the specific typeof loudness processing but the control bits from validator 203 indicatethat the LPSM are not valid).

Alternatively, decoder 200 asserts metadata extracted by decoder 202from the input bitstream, and metadata extracted by parser 205 from theinput bitstream to post-processor 300, and post-processor 300 performsadaptive processing on the decoded audio data using the metadata, orperforms validation of the metadata and then performs adaptiveprocessing on the decoded audio data using the metadata if thevalidation indicates that the metadata are valid.

In some embodiments, if decoder 200 receives an audio bitstreamgenerated in accordance with an embodiment of the invention withcryptographic hash, the decoder is configured to parse and retrieve thecryptographic hash from a data block determined from the bitstream, saidblock comprising loudness processing state metadata (LPSM). Validator203 may use the cryptographic hash to validate the received bitstreamand/or associated metadata. For example, if validator 203 finds the LPSMto be valid based on a match between a reference cryptographic hash andthe cryptographic hash retrieved from the data block, then it may signalto a downstream audio processing unit (e.g., post-processor 300, whichmay be or include a volume leveling unit) to pass through (unchanged)the audio data of the bitstream. Additionally, optionally, oralternatively, other types of cryptographic techniques may be used inplace of a method based on a cryptographic hash.

In some implementations of decoder 200, the encoded bitstream received(and buffered in memory 201) is an AC-3 bitstream or an E-AC-3bitstream, and comprises audio data segments (e.g., the AB0-AB5 segmentsof the frame shown in FIG. 4) and metadata segments, where the audiodata segments are indicative of audio data, and each of at least some ofthe metadata segments includes PIM or SSM (or other metadata). Decoderstage 202 (and/or parser 205) is configured to extract the metadata fromthe bitstream. Each of the metadata segments which includes PIM and/orSSM (and optionally also other metadata) is included in a waste bitsegment of a frame of the bitstream, or an “addbsi” field of theBitstream Information (“BSI”) segment of a frame of the bitstream, or inan auxdata field (e.g., the AUX segment shown in FIG. 4) at the end of aframe of the bitstream. A frame of the bitstream may include one or twometadata segments, each of which includes metadata, and if the frameincludes two metadata segments, one may be present in the addbsi fieldof the frame and the other in the AUX field of the frame.

In some embodiments, each metadata segment (sometimes referred to hereinas a “container”) of the bitstream buffered in buffer 201 has a formatwhich includes a metadata segment header (and optionally also othermandatory or “core” elements), and one or more metadata payloadsfollowing the metadata segment header. SIM, if present, is included inone of the metadata payloads (identified by a payload header, andtypically having format of a first type). PIM, if present, is includedin another one of the metadata payloads (identified by a payload headerand typically having format of a second type). Similarly, each othertype of metadata (if present) is included in another one of the metadatapayloads (identified by a payload header and typically having formatspecific to the type of metadata). The exemplary format allowsconvenient access to the SSM, PIM, and other metadata at times otherthan during decoding (e.g., by post-processor 300 following decoding, orby a processor configured to recognize the metadata without performingfull decoding on the encoded bitstream), and allows convenient andefficient error detection and correction (e.g., of substreamidentification) during decoding of the bitstream. For example, withoutaccess to SSM in the exemplary format, decoder 200 might incorrectlyidentify the correct number of substreams associated with a program. Onemetadata payload in a metadata segment may include SSM, another metadatapayload in the metadata segment may include PIM, and optionally also atleast one other metadata payload in the metadata segment may includeother metadata (e.g., loudness processing state metadata or “LPSM”).

In some embodiments, a substream structure metadata (SSM) payloadincluded in a frame of an encoded bitstream (e.g., an E-AC-3 bitstreamindicative of at least one audio program) buffered in buffer 201includes SSM in the following format:

a payload header, typically including at least one identification value(e.g., a 2-bit value indicative of SSM format version, and optionallyalso length, period, count, and substream association values); and afterthe header:

independent substream metadata indicative of the number of independentsubstreams of the program indicated by the bitstream; and

dependent substream metadata indicative of whether each independentsubstream of the program has at least one dependent substream associatedwith it, and if so the number of dependent substreams associated witheach independent substream of the program.

In some embodiments, a program information metadata (PIM) payloadincluded in a frame of an encoded bitstream (e.g., an E-AC-3 bitstreamindicative of at least one audio program) buffered in buffer 201 has thefollowing format:

a payload header, typically including at least one identification value(e.g., a value indicative of PIM format version, and optionally alsolength, period, count, and substream association values); and after theheader, PIM in the following format:

active channel metadata of each silent channel and each non-silentchannel of an audio program (i.e., which channel(s) of the programcontain audio information, and which (if any) contain only silence(typically for the duration of the frame)). In embodiments in which theencoded bitstream is an AC-3 or E-AC-3 bitstream, the active channelmetadata in a frame of the bitstream may be used in conjunction withadditional metadata of the bitstream (e.g., the audio coding mode(“acmod”) field of the frame, and, if present, the chanmap field in theframe or associated dependent substream frame(s)) to determine whichchannel(s) of the program contain audio information and which containsilence;

downmix processing state metadata indicative of whether the program wasdownmixed (prior to or during encoding), and if so, the type ofdownmixing that was applied. Downmix processing state metadata may beuseful for implementing upmixing (e.g., in post-processor 300)downstream of a decoder, for example to upmix the audio content of theprogram using parameters that most closely match a type of downmixingthat was applied. In embodiments in which the encoded bitstream is anAC-3 or E-AC-3 bitstream, the downmix processing state metadata may beused in conjunction with the audio coding mode (“acmod”) field of theframe to determine the type of downmixing (if any) applied to thechannel(s) of the program;

upmix processing state metadata indicative of whether the program wasupmixed (e.g., from a smaller number of channels) prior to or duringencoding, and if so, the type of upmixing that was applied. Upmixprocessing state metadata may be useful for implementing downmixing (ina post-processor) downstream of a decoder, for example to downmix theaudio content of the program in a manner that is compatible with a typeof upmixing (e.g., Dolby Pro Logic, or Dolby Pro Logic II Movie Mode, orDolby Pro Logic II Music Mode, or Dolby Professional Upmixer) that wasapplied to the program. In embodiments in which the encoded bitstream isan E-AC-3 bitstream, the upmix processing state metadata may be used inconjunction with other metadata (e.g., the value of a “strmtyp” field ofthe frame) to determine the type of upmixing (if any) applied to thechannel(s) of the program. The value of the “strmtyp” field (in the BSIsegment of a frame of an E-AC-3 bitstream) indicates whether audiocontent of the frame belongs to an independent stream (which determinesa program) or an independent substream (of a program which includes oris associated with multiple substreams) and thus may be decodedindependently of any other substream indicated by the E-AC-3 bitstream,or whether audio content of the frame belongs to a dependent substream(of a program which includes or is associated with multiple substreams)and thus must be decoded in conjunction with an independent substreamwith which it is associated; and preprocessing state metadata indicativeof whether preprocessing was performed on audio content of the frame(before encoding of the audio content to generated the encodedbitstream), and if so the type of preprocessing that was performed.

In some implementations, the preprocessing state metadata is indicativeof:

whether surround attenuation was applied (e.g., whether surroundchannels of the audio program were attenuated by 3 dB prior toencoding),

whether 90 degree phase shift applied (e.g., to surround channels Ls andRs channels of the audio program prior to encoding),

whether a low-pass filter was applied to an LFE channel of the audioprogram prior to encoding,

whether level of an LFE channel of the program was monitored duringproduction and if so the monitored level of the LFE channel relative tolevel of the full range audio channels of the program,

whether dynamic range compression should be performed (e.g., in thedecoder) on each block of decoded audio content of the program and if sothe type (and/or parameters) of dynamic range compression to beperformed (e.g., this type of preprocessing state metadata may beindicative of which of the following compression profile types wasassumed by the encoder to generate dynamic range compression controlvalues that are included in the encoded bitstream: Film Standard, FilmLight, Music Standard, Music Light, or Speech. Alternatively, this typeof preprocessing state metadata may indicate that heavy dynamic rangecompression (“compr” compression) should be performed on each frame ofdecoded audio content of the program in a manner determined by dynamicrange compression control values that are included in the encodedbitstream),

whether spectral extension processing and/or channel coupling encodingwas employed to encode specific frequency ranges of content of theprogram and if so the minimum and maximum frequencies of the frequencycomponents of the content on which spectral extension encoding wasperformed, and the minimum and maximum frequencies of frequencycomponents of the content on which channel coupling encoding wasperformed. This type of preprocessing state metadata information may beuseful to perform equalization (in a post-processor) downstream of adecoder. Both channel coupling and spectral extension information arealso useful for optimizing quality during transcode operations andapplications. For example, an encoder may optimize its behavior(including the adaptation of pre-processing steps such as headphonevirtualization, up mixing, etc.) based on the state of parameters, suchas spectral extension and channel coupling information. Moreover, theencoder may would adapt its coupling and spectral extension parametersdynamically to match and/or to optimal values based on the state of theinbound (and authenticated) metadata, and

whether dialog enhancement adjustment range data is included in theencoded bitstream, and if so the range of adjustment available duringperformance of dialog enhancement processing (e.g., in a post-processordownstream of a decoder) to adjust the level of dialog content relativeto the level of non-dialog content in the audio program.

In some embodiments, an LPSM payload included in a frame of an encodedbitstream (e.g., an E-AC-3 bitstream indicative of at least one audioprogram) buffered in buffer 201 includes LPSM in the following format:

a header (typically including a syncword identifying the start of theLPSM payload, followed by at least one identification value, e.g., theLPSM format version, length, period, count, and substream associationvalues indicated in Table 2 below); and

after the header,

at least one dialog indication value (e.g., parameter “Dialogchannel(s)” of Table 2) indicating whether corresponding audio dataindicates dialog or does not indicate dialog (e.g., which channels ofcorresponding audio data indicate dialog);

at least one loudness regulation compliance value (e.g., parameter“Loudness Regulation Type” of Table 2) indicating whether correspondingaudio data complies with an indicated set of loudness regulations;

at least one loudness processing value (e.g., one or more of parameters“Dialog gated Loudness Correction flag,” “Loudness Correction Type,” ofTable 2) indicating at least one type of loudness processing which hasbeen performed on the corresponding audio data; and

at least one loudness value (e.g., one or more of parameters “ITURelative Gated Loudness,” “ITU Speech Gated Loudness,” “ITU (EBU 3341)Short-term 3 s Loudness,” and “True Peak” of Table 2) indicating atleast one loudness (e.g., peak or average loudness) characteristic ofthe corresponding audio data.

In some implementations, parser 205 (and/or decoder stage 202) isconfigured to extract, from a waste bit segment, or an “addbsi” field,or an auxdata field, of a frame of the bitstream, each metadata segmenthaving the following format:

a metadata segment header (typically including a syncword identifyingthe start of the metadata segment, followed by at least oneidentification value, e.g., version, length, and period, expandedelement count, and substream association values); and

after the metadata segment header, at least one protection value (e.g.,the HMAC digest and Audio Fingerprint values of Table 1) useful for atleast one of decryption, authentication, or validation of at least oneof metadata of the metadata segment or the corresponding audio data);and

also after the metadata segment header, metadata payload identification(“ID”) and payload configuration values which identify the type and atleast one aspect of the configuration (e.g., size) of each followingmetadata payload.

Each metadata payload segment (preferably having the above-specifiedformat) follows the corresponding metadata payload ID and payloadconfiguration values.

More generally, the encoded audio bitstream generated by preferredembodiments of the invention has a structure which provides a mechanismto label metadata elements and sub-elements as core (mandatory) orexpanded (optional) elements or sub-elements. This allows the data rateof the bitstream (including its metadata) to scale across numerousapplications. The core (mandatory) elements of the preferred bitstreamsyntax should also be capable of signaling that expanded (optional)elements associated with the audio content are present (in-band) and/orin a remote location (out of band).

Core element(s) are required to be present in every frame of thebitstream. Some sub-elements of core elements are optional and may bepresent in any combination. Expanded elements are not required to bepresent in every frame (to limit bitrate overhead). Thus, expandedelements may be present in some frames and not others. Some sub-elementsof an expanded element are optional and may be present in anycombination, whereas some sub-elements of an expanded element may bemandatory (i.e., if the expanded element is present in a frame of thebitstream).

In a class of embodiments, an encoded audio bitstream comprising asequence of audio data segments and metadata segments is generated(e.g., by an audio processing unit which embodies the invention). Theaudio data segments are indicative of audio data, each of at least someof the metadata segments includes PIM and/or SSM (and optionally alsometadata of at least one other type), and the audio data segments aretime-division multiplexed with the metadata segments. In preferredembodiments in this class, each of the metadata segments has a preferredformat to be described herein.

In one preferred format, the encoded bitstream is an AC-3 bitstream oran E-AC-3 bitstream, and each of the metadata segments which includesSSM and/or PIM is included (e.g., by stage 107 of a preferredimplementation of encoder 100) as additional bit stream information inthe “addbsi” field (shown in FIG. 6) of the Bitstream Information(“BSI”) segment of a frame of the bitstream, or in an auxdata field of aframe of the bitstream, or in a waste bit segment of a frame of thebitstream.

In the preferred format, each of the frames includes a metadata segment(sometimes referred to herein as a metadata container, or container) ina waste bit segment (or addbsi field) of the frame. The metadata segmenthas the mandatory elements (collectively referred to as the “coreelement”) shown in Table 1 below (and may include the optional elementsshown in Table 1). At least some of the required elements shown in Table1 are included in the metadata segment header of the metadata segmentbut some may be included elsewhere in the metadata segment:

TABLE 1 Mandatory/ Parameter Description Optional SYNC [ID] M Coreelement version M Core element length M Core element period M (xxx)Expanded element Indicates the number of M count expanded metadataelements associated with the core element. This value mayincrement/decrement as the bitstream is passed from production throughdistribution and final emission. Substream association Describes which Msubstream(s) the core element is associated with. Signature (HMAC256-bit HMAC digest (using M digest) SHA-2 algorithm) computed over theaudio data, the core element, and all expanded elements, of the entireframe. PGM boundary Field only appears for some O countdown number offrames at the head or tail of an audio program file/stream. Thus, a coreelement version change could be used to signal the inclusion of thisparameter. Audio Fingerprint Audio Fingerprint taken over O some numberof PCM audio samples represented by the core element period field. VideoFingerprint Video Fingerprint taken over O some number of compressedvideo samples (if any) represented by the core element period field.URL/UUID This field is defined to carry O a URL and/or a UUID (it may beredundant to the fingerprint) that references an external location ofadditional program content (essence) and/or metadata associated with thebitstream.

In the preferred format, each metadata segment (in a waste bit segmentor addbsi or auxdata field of a frame of an encoded bitstream) whichcontains SSM, PIM, or LPSM contains a metadata segment header (andoptionally also additional core elements), and after the metadatasegment header (or the metadata segment header and other core elements),one or more metadata payloads. Each metadata payload includes a metadatapayload header (indicating a specific type of metadata (e.g., SSM, PIM,or LPSM) included in the payload, followed by metadata of the specifictype. Typically, the metadata payload header includes the followingvalues (parameters):

a payload ID (identifying the type of metadata, e.g., SSM, PIM, or LPSM)following the metadata segment header (which may include valuesspecified in Table 1);

a payload configuration value (typically indicating the size of thepayload) following the payload ID;

and optionally also, additional payload configuration values (e.g., anoffset value indicating number of audio samples from the start of theframe to the first audio sample to which the payload pertains, andpayload priority value, e.g., indicating a condition in which thepayload may be discarded).

Typically, the metadata of the payload has one of the following formats:

the metadata of the payload is SSM, including independent substreammetadata indicative of the number of independent substreams of theprogram indicated by the bitstream; and dependent substream metadataindicative of whether each independent substream of the program has atleast one dependent substream associated with it, and if so the numberof dependent substreams associated with each independent substream ofthe program;

the metadata of the payload is PIM, including active channel metadataindicative of which channel(s) of an audio program contain audioinformation, and which (if any) contain only silence (typically for theduration of the frame); downmix processing state metadata indicative ofwhether the program was downmixed (prior to or during encoding), and ifso, the type of downmixing that was applied, upmix processing statemetadata indicative of whether the program was upmixed (e.g., from asmaller number of channels) prior to or during encoding, and if so, thetype of upmixing that was applied, and preprocessing state metadataindicative of whether preprocessing was performed on audio content ofthe frame (before encoding of the audio content to generated the encodedbitstream), and if so the type of preprocessing that was performed; or

the metadata of the payload is LPSM having format as indicated in thefollowing table (Table 2):

TABLE 2 Insertion LPSM number Rate (Period Parameter of of updating[Intelligent Descrip- unique Mandatory/ of the Loudness] tion statesOptional parameter) LPSM M version LPSM Applicable M period to xxx (xxx)fields only LPSM M count LPSM M substream association Dialog Indicates 8 M ~0.5 channel(s) which seconds combination (typical) of L, C & Raudio channels contain speech over the previous 0.5 seconds. When,speech is not present in any L, C or R combination, then this parametershall indicate “no dialog” Loudness Indicates  8 M Frame Regulation thatthe Type associated audio data stream is in compliance with a specificset of regulations (e.g., ATSC A/85 or EBU R128) Dialog Indicates  2 O(only present if Frame gated if the Loudness_Regulation_ Loudnessassociated Type indicates that Correction audio the corresponding flagstream has audio is been UNCORRECTED) corrected based on dialog gatingLoudness Indicates  2 O (only present if Frame Correction if theLoudness_Regulation_ Type associated Type indicates that audio thecorresponding stream has audio is been UNCORRECTED) corrected with aninfinite look- ahead (file- based) or with a realtime (RT) loudness anddynamic range controller. ITU Indicates 128 O   1 sec Relative the ITU-RGated BS.1770-3 Loudness integrated (INF) loudness of the associatedaudio stream w/o metadata applied (e.g., 7 bits: −58 -> +5.5 LKFS 0.5LKFS steps) ITU Indicates 128 O   1 sec Speech the ITU-R GatedBS.1770-1/3 Loudness integrated (INF) loudness of the speech/ dialog ofthe associated audio stream w/o metadata applied (e.g., 7 bits: −58 ->+5.5 LKFS 0.5 LKFS steps) ITU (EBU Indicates 256 O 0.1 sec 3341) the 3-Short-term second 3 s ungated Loudness ITU (ITU- BS.1771-1) loudness ofthe associated audio stream w/o metadata applied (sliding window) @ ~10Hz insertion rate (e.g., 8 bits: 116 -> +11.5 LKFS 0.5 LKFS steps) TruePeak Indicates 256 O 0.5 sec value the ITU-R BS.1770-3 Annex 2 TruePeakvalue (dBTP) of the associated audio stream w/o metadata applied. (i.e.,largest value over frame period signaled in element period field) 116 ->+11.5 LKFS 0.5 LKFS steps Downmix Indicates Offset downmix loudnessoffset Program Indicates, Boundary in frames, when a program boundarywill or has occurred. When program boundary is not at frame boundary,optional sample offset will indicate how far in frame actual programboundary occurs

In another preferred format of an encoded bitstream generated inaccordance with the invention, the bitstream is an AC-3 bitstream or anE-AC-3 bitstream, and each of the metadata segments which includes PIMand/or SSM (and optionally also metadata of at least one other type) isincluded (e.g., by stage 107 of a preferred implementation of encoder100) in any of: a waste bit segment of a frame of the bitstream; or an“addbsi” field (shown in FIG. 6) of the Bitstream Information (“BSI”)segment of a frame of the bitstream; or an auxdata field (e.g., the AUXsegment shown in FIG. 4) at the end of a frame of the bitstream. A framemay include one or two metadata segments, each of which includes PIMand/or SSM, and (in some embodiments) if the frame includes two metadatasegments, one may be present in the addbsi field of the frame and theother in the AUX field of the frame. Each metadata segment preferablyhas the format specified above with reference to Table 1 above (i.e., itincludes the core elements specified in Table 1, followed by payload ID(identifying type of metadata in each payload of the metadata segment)and payload configuration values, and each metadata payload). Eachmetadata segment including LPSM preferably has the format specifiedabove with reference to Tables 1 and 2 above (i.e., it includes the coreelements specified in Table 1, followed by payload ID (identifying themetadata as LPSM) and payload configuration values, followed by thepayload (LPSM data which has format as indicated in Table 2)).

In another preferred format, the encoded bitstream is a Dolby Ebitstream, and each of the metadata segments which includes PIM and/orSSM (and optionally also other metadata) is the first N sample locationsof the Dolby E guard band interval. A Dolby E bitstream including such ametadata segment which includes LPSM preferably includes a valueindicative of LPSM payload length signaled in the Pd word of the SMPTE337M preamble (the SMPTE 337M Pa word repetition rate preferably remainsidentical to associated video frame rate).

In a preferred format, in which the encoded bitstream is an E-AC-3bitstream, each of the metadata segments which includes PIM and/or SSM(and optionally also LPSM and/or other metadata) is included (e.g., bystage 107 of a preferred implementation of encoder 100) as additionalbitstream information in a waste bit segment, or in the “addbsi” fieldof the Bitstream Information (“BSI”) segment, of a frame of thebitstream. We next describe additional aspects of encoding an E-AC-3bitstream with LPSM in this preferred format:

-   1. during generation of an E-AC-3 bitstream, while the E-AC-3    encoder (which inserts the LPSM values into the bitstream) is    “active,” for every frame (syncframe) generated, the bitstream    should include a metadata block (including LPSM) carried in the    addbsi field (or waste bit segment) of the frame. The bits required    to carry the metadata block should not increase the encoder bitrate    (frame length);-   2. Every metadata block (containing LPSM) should contain the    following information:

loudness_correction_type_flag: where ‘1’ indicates the loudness of thecorresponding audio data was corrected upstream from the encoder, and‘0’ indicates the loudness was corrected by a loudness correctorembedded in the encoder (e.g., loudness processor 103 of encoder 100 ofFIG. 2);

speech_channel: indicates which source channel(s) contain speech (overthe previous 0.5 sec). If no speech is detected, this shall be indicatedas such;

speech_loudness: indicates the integrated speech loudness of eachcorresponding audio channel which contains speech (over the previous 0.5sec);

ITU_loudness: indicates the integrated ITU BS.1770-3 loudness of eachcorresponding audio channel; and

gain: loudness composite gain(s) for reversal in a decoder (todemonstrate reversibility);

-   3. While the E-AC-3 encoder (which inserts the LPSM values into the    bitstream) is “active” and is receiving an AC-3 frame with a ‘trust’    flag, the loudness controller in the encoder (e.g., loudness    processor 103 of encoder 100 of FIG. 2) should be bypassed. The    ‘trusted’ source dialnorm and DRC values should be passed through    (e.g., by generator 106 of encoder 100) to the E-AC-3 encoder    component (e.g., stage 107 of encoder 100). The LPSM block    generation continues and the loudness_correction_type_flag is set to    ‘1’. The loudness controller bypass sequence must be synchronized to    the start of the decoded AC-3 frame where the ‘trust’ flag appears.    The loudness controller bypass sequence should be implemented as    follows: the leveler_amount control is decremented from a value of 9    to a value of 0 over 10 audio block periods (i.e. 53.3 msec) and the    leveler_back_end_meter control is placed into bypass mode (this    operation should result in a seamless transition). The term    “trusted” bypass of the leveler implies that the source bitstream's    dialnorm value is also re-utilized at the output of the encoder.    (e.g. if the ‘trusted’ source bitstream has a dialnorm value of −30    then the output of the encoder should utilize −30 for the outbound    dialnorm value);-   4. While the E-AC-3 encoder (which inserts the LPSM values into the    bitstream) is “active” and is receiving an AC-3 frame without the    ‘trust’ flag, the loudness controller embedded in the encoder (e.g.,    loudness processor 103 of encoder 100 of FIG. 2) should be active.    LPSM block generation continues and the    loudness_correction_type_flag is set to ‘0’. The loudness controller    activation sequence should be synchronized to the start of the    decoded AC-3 frame where the ‘trust’ flag disappears. The loudness    controller activation sequence should be implemented as follows: the    leveler_amount control is incremented from a value of 0 to a value    of 9 over 1 audio block period. (i.e. 5.3 msec) and the    leveler_back_end_meter control is placed into ‘active’ mode (this    operation should result in a seamless transition and include a    back_end_meter integration reset); and-   5. during encoding, a graphic user interface (GUI) should indicate    to a user the following parameters: “Input Audio Program:    [Trusted/Untrusted]”—the state of this parameter is based on the    presence of the “trust” flag within the input signal; and “Real-time    Loudness Correction: [Enabled/Disabled]”—the state of this parameter    is based on the whether this loudness controller embedded in the    encoder is active.

When decoding an AC-3 or E-AC-3 bitstream which has LPSM (in thepreferred format) included in a waste bit or skip field segment, or the“addbsi” field of the Bitstream Information (“BSI”) segment, of eachframe of the bitstream, the decoder should parse the LPSM block data (inthe waste bit segment or addbsi field) and pass all of the extractedLPSM values to a graphic user interface (GUI). The set of extracted LPSMvalues is refreshed every frame.

In another preferred format of an encoded bitstream generated inaccordance with the invention, the encoded bitstream is an AC-3bitstream or an E-AC-3 bitstream, and each of the metadata segmentswhich includes PIM and/or SSM (and optionally also LPSM and/or othermetadata) is included (e.g., by stage 107 of a preferred implementationof encoder 100) in a waste bit segment, or in an Aux segment, or asadditional bit stream information in the “addbsi” field (shown in FIG.6) of the Bitstream Information (“BSI”) segment, of a frame of thebitstream. In this format (which is a variation on the format describedabove with references to Tables 1 and 2), each of the addbsi (or Aux orwaste bit) fields which contains LPSM contains the following LPSMvalues:

the core elements specified in Table 1, followed by payload ID(identifying the metadata as LPSM) and payload configuration values,followed by the payload (LPSM data) which has the following format(similar to the mandatory elements indicated in Table 2 above):

version of LPSM payload: a 2-bit field which indicates the version ofthe LPSM payload;

dialchan: a 3-bit field which indicates whether the Left, Right and/orCenter channels of corresponding audio data contain spoken dialog. Thebit allocation of the dialchan field may be as follows: bit 0, whichindicates the presence of dialog in the left channel, is stored in themost significant bit of the dialchan field; and bit 2, which indicatesthe presence of dialog in the center channel, is stored in the leastsignificant bit of the dialchan field.

Each bit of the dialchan field is set to ‘1’ if the correspondingchannel contains spoken dialog during the preceding 0.5 seconds of theprogram;

loudregtyp: a 4-bit field which indicates which loudness regulationstandard the program loudness complies with. Setting the “loudregtyp”field to ‘000’ indicates that the LPSM does not indicate loudnessregulation compliance. For example, one value of this field (e.g., 0000)may indicate that compliance with a loudness regulation standard is notindicated, another value of this field (e.g., 0001) may indicate thatthe audio data of the program complies with the ATSC A/85 standard, andanother value of this field (e.g., 0010) may indicate that the audiodata of the program complies with the EBU R128 standard. In the example,if the field is set to any value other than ‘0000’, the loudcorrdialgatand loudcorrtyp fields should follow in the payload;

loudcorrdialgat: a one-bit field which indicates if dialog-gatedloudness correction has been applied. If the loudness of the program hasbeen corrected using dialog gating, the value of the loudcorrdialgatfield is set to ‘1’. Otherwise it is set to ‘0’;

loudcorrtyp: a one-bit field which indicates type of loudness correctionapplied to the program. If the loudness of the program has beencorrected with an infinite look-ahead (file-based) loudness correctionprocess, the value of the loudcorrtyp field is set to ‘0’. If theloudness of the program has been corrected using a combination ofrealtime loudness measurement and dynamic range control, the value ofthis field is set to ‘1’;

loudrelgate: a one-bit field which indicates whether relative gatedloudness data (ITU) exists. If the loudrelgate field is set to ‘1’, a7-bit ituloudrelgat field should follow in the payload;

loudrelgat: a 7-bit field which indicates relative gated programloudness (ITU). This field indicates the integrated loudness of theaudio program, measured according to ITU-R BS.1770-3 without any gainadjustments due to dialnorm and dynamic range compression (DRC) beingapplied. The values of 0 to 127 are interpreted as −58 LKFS to +5.5LKFS, in 0.5 LKFS steps;

loudspchgate: a one-bit field which indicates whether speech-gatedloudness data (ITU) exists. If the loudspchgate field is set to ‘1’, a7-bit loudspchgat field should follow in the payload;

loudspchgat: a 7-bit field which indicates speech-gated programloudness. This field indicates the integrated loudness of the entirecorresponding audio program, measured according to formula (2) of ITU-RBS.1770-3 and without any gain adjustments due to dialnorm and dynamicrange compression being applied. The values of 0 to 127 are interpretedas −58 to +5.5 LKFS, in 0.5 LKFS steps;

loudstrm3 se: a one-bit field which indicates whether short-term (3second) loudness data exists. If the field is set to ‘1’, a 7-bitloudstrm3 s field should follow in the payload;

loudstrm3 s: a 7-bit field which indicates the ungated loudness of thepreceding 3 seconds of the corresponding audio program, measuredaccording to ITU-R BS.1771-1 and without any gain adjustments due todialnorm and dynamic range compression being applied. The values of 0 to256 are interpreted as −116 LKFS to +11.5 LKFS in 0.5 LKFS steps;

truepke: a one-bit field which indicates whether true peak loudness dataexists. If the truepke field is set to ‘1’, an 8-bit truepk field shouldfollow in the payload; and

truepk: an 8-bit field which indicates the true peak sample value of theprogram, measured according to Annex 2 of ITU-R BS.1770-3 and withoutany gain adjustments due to dialnorm and dynamic range compression beingapplied. The values of 0 to 256 are interpreted as −116 LKFS to +11.5LKFS in 0.5 LKFS steps.

In some embodiments, the core element of a metadata segment in a wastebit segment or in an auxdata (or “addbsi”) field of a frame of an AC-3bitstream or an E-AC-3 bitstream comprises a metadata segment header(typically including identification values, e.g., version), and afterthe metadata segment header: values indicative of whether fingerprintdata is (or other protection values are) included for metadata of themetadata segment, values indicative of whether external data (related toaudio data corresponding to the metadata of the metadata segment)exists, payload ID and payload configuration values for each type ofmetadata (e.g., PIM and/or SSM and/or LPSM and/or metadata of a type)identified by the core element, and protection values for at least onetype of metadata identified by the metadata segment header (or othercore elements of the metadata segment). The metadata payload(s) of themetadata segment follow the metadata segment header, and are (in somecases) nested within core elements of the metadata segment.

Embodiments of the present invention may be implemented in hardware,firmware, or software, or a combination of both (e.g., as a programmablelogic array). Unless otherwise specified, the algorithms or processesincluded as part of the invention are not inherently related to anyparticular computer or other apparatus. In particular, variousgeneral-purpose machines may be used with programs written in accordancewith the teachings herein, or it may be more convenient to constructmore specialized apparatus (e.g., integrated circuits) to perform therequired method steps. Thus, the invention may be implemented in one ormore computer programs executing on one or more programmable computersystems (e.g., an implementation of any of the elements of FIG. 1, orencoder 100 of FIG. 2 (or an element thereof), or decoder 200 of FIG. 3(or an element thereof), or post-processor 300 of FIG. 3 (or an elementthereof)) each comprising at least one processor, at least one datastorage system (including volatile and non-volatile memory and/orstorage elements), at least one input device or port, and at least oneoutput device or port. Program code is applied to input data to performthe functions described herein and generate output information. Theoutput information is applied to one or more output devices, in knownfashion.

Each such program may be implemented in any desired computer language(including machine, assembly, or high level procedural, logical, orobject oriented programming languages) to communicate with a computersystem. In any case, the language may be a compiled or interpretedlanguage.

For example, when implemented by computer software instructionsequences, various functions and steps of embodiments of the inventionmay be implemented by multithreaded software instruction sequencesrunning in suitable digital signal processing hardware, in which casethe various devices, steps, and functions of the embodiments maycorrespond to portions of the software instructions.

Each such computer program is preferably stored on or downloaded to astorage media or device (e.g., solid state memory or media, or magneticor optical media) readable by a general or special purpose programmablecomputer, for configuring and operating the computer when the storagemedia or device is read by the computer system to perform the proceduresdescribed herein. The inventive system may also be implemented as acomputer-readable storage medium, configured with (i.e., storing) acomputer program, where the storage medium so configured causes acomputer system to operate in a specific and predefined manner toperform the functions described herein.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention.Numerous modifications and variations of the present invention arepossible in light of the above teachings. It is to be understood thatwithin the scope of the appended claims, the invention may be practicedotherwise than as specifically described herein.

What is claimed is:
 1. An audio processing method, comprising: receivinga block of encoded audio data; receiving encoded audio metadataassociated with the block of audio data; performing a cryptographic hashon the audio metadata and on at least a portion of the audio data, toproduce a currently-computed hash; retrieving, from a data fieldassociated with the encoded audio metadata, a previously-computed hash;and performing an authentication process that involves comparing thecurrently-computed hash with the previously-computed hash.
 2. The audioprocessing method of claim 1, further comprising disabling or alteringat least one operation to be performed on the audio data if theauthentication process succeeds.
 3. The audio processing method of claim1, wherein the metadata comprises dynamic range compression metadata. 4.The audio processing method of claim 1, wherein the metadata comprisesloudness processing state metadata.
 5. The audio processing method ofclaim 1, further comprising decoding at least a portion of the audiometadata or the audio data.
 6. A non-transitory medium having softwarestored thereon, the software including instructions for performing anaudio processing method, the audio processing method comprising:receiving a block of encoded audio data; receiving encoded audiometadata associated with the block of audio data; performing acryptographic hash on the audio metadata and on at least a portion ofthe audio data, to produce a currently-computed hash; retrieving, from adata field associated with the encoded audio metadata, apreviously-computed hash; and performing an authentication process thatinvolves comparing the currently-computed hash with thepreviously-computed hash.
 7. The non-transitory medium of claim 6,wherein the audio processing method further comprises disabling oraltering at least one operation to be performed on the audio data if theauthentication process succeeds.
 8. The non-transitory medium of claim6, wherein the metadata comprises dynamic range compression metadata. 9.The non-transitory medium of claim 6, wherein the metadata comprisesloudness processing state metadata.
 10. The non-transitory medium ofclaim 6, wherein the audio processing method further comprises decodingat least a portion of the audio metadata or the audio data.
 11. An audioprocessing unit comprising at least one processor configured for:receiving a block of encoded audio data; receiving encoded audiometadata associated with the block of audio data; performing acryptographic hash on the audio metadata and on at least a portion ofthe audio data, to produce a currently-computed hash; retrieving, from adata field associated with the encoded audio metadata, apreviously-computed hash; and performing an authentication process thatinvolves comparing the currently-computed hash with thepreviously-computed hash.
 12. The audio processing unit of claim 11,wherein the at least one processor is configured for disabling oraltering at least one operation to be performed on the audio data if theauthentication process succeeds.
 13. The audio processing unit of claim11, wherein the metadata comprises dynamic range compression metadata.14. The audio processing unit of claim 11, wherein the metadatacomprises loudness processing state metadata.
 15. The audio processingunit of claim 11, wherein the at least one processor is configured fordecoding at least a portion of the audio metadata or the audio data. 16.An audio processing unit, comprising: means for receiving a block ofencoded audio data; means for receiving encoded audio metadataassociated with the block of audio data; means for performing acryptographic hash on the audio metadata and on at least a portion ofthe audio data, to produce a currently-computed hash; means forretrieving, from a data field associated with the encoded audiometadata, a previously-computed hash; and means for performing anauthentication process that involves comparing the currently-computedhash with the previously-computed hash.
 17. The audio processing unit ofclaim 16, further comprising means for disabling or altering at leastone operation to be performed on the audio data if the authenticationprocess succeeds.
 18. The audio processing unit of claim 16, wherein themetadata comprises dynamic range compression metadata.
 19. The audioprocessing unit of claim 16, wherein the metadata comprises loudnessprocessing state metadata.
 20. The audio processing unit of claim 16,further comprising means for decoding at least a portion of the audiometadata or the audio data.